Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1775

reference: 245-tree-1
name: 1775
tree-preservation-order: undefined
245-tpo-1
uprn
address-text
point: POINT (-1.004236 50.854994)
geometry: MULTIPOLYGON (((-1.004208 50.854991,-1.004209 50.854997,-1.004213 50.855002,-1.004227 50.855009,-1.004245 50.855009,-1.004253 50.855006,-1.004259 50.855002,-1.004265 50.854992,-1.004264 50.854986,-1.004260 50.854981,-1.004246 50.854974,-1.004228 50.854974,-1.004220 50.854977,-1.004214 50.854981,-1.004208 50.854991)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL